home *** CD-ROM | disk | FTP | other *** search
-
-
-
- MMMMKKKKAAAAFFFF((((1111)))) MMMMKKKKAAAAFFFF((((1111))))
-
-
-
- NNNNAAAAMMMMEEEE
- mmmmkkkkaaaaffff - create a Performance Co-Pilot archive folio
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- $$$$PPPPCCCCPPPP____BBBBIIIINNNNAAAADDDDMMMM____DDDDIIIIRRRR////mmmmkkkkaaaaffff [_f_i_n_d_o_p_t_s] _f_i_l_e_n_a_m_e ...
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- A collection of one or more Performance Co-Pilot (see PPPPCCCCPPPPIIIInnnnttttrrrroooo(1))
- archive logs may be combined with mmmmkkkkaaaaffff to produce a PCP archive folio and
- the associated archive folio control file. Some PCP tools use mmmmkkkkaaaaffff to
- create archive folios, e.g. the ``record'' facility in the ppppmmmmcccchhhhaaaarrrrtttt(1),
- ppppmmmmvvvviiiieeeewwww(1) and oooovvvviiiieeeewwww(1) tools, to facilitate playback with ppppmmmmaaaaffffmmmm(1).
-
- mmmmkkkkaaaaffff processes each _f_i_l_e_n_a_m_e argument, and if this is a component file
- from a PCP archive that archive is added to the folio.
-
- If _f_i_l_e_n_a_m_e is a directory, then this is searched recursively using
- ffffiiiinnnndddd(1). Any _f_i_l_e_n_a_m_e argument beginning with a ``-'' is assumed to be a
- ffffiiiinnnndddd(1) command line option (_f_i_n_d_o_p_t_s); the default is ----ffffoooolllllllloooowwww if no
- _f_i_n_d_o_p_t_s are specified.
-
- The first named archive in the folio is assumed to be associated with the
- default host for any tool that tries to replay multiple archives from the
- folio.
-
- The folio control file is written to standard output, and has the
- following format.
-
- 1. The first line contains the word PPPPCCCCPPPPFFFFoooolllliiiioooo.
-
- 2. The second line contains the tag VVVVeeeerrrrssssiiiioooonnnn:::: followed by the format
- version number (currently 1).
-
- 3. For subsequent lines, blank lines and lines beginning with ``#'' are
- ignored.
-
- 4. The line beginning with the tag CCCCrrrreeeeaaaatttteeeedddd:::: documents where and when the
- folio was created.
-
- 5. The line beginning with the tag CCCCrrrreeeeaaaattttoooorrrr:::: identifies the tool which
- created the folio (and is assumed to know how to replay the archive
- folio). If present, the second argument is the name of a
- configuration file that the creator tool could use to replay the
- archive folio, e.g. with the rrrreeeeppppllllaaaayyyy command for ppppmmmmaaaaffffmmmm(1). In the case
- of mmmmkkkkaaaaffff (unlike ppppmmmmcccchhhhaaaarrrrtttt(1) or ppppmmmmvvvviiiieeeewwww(1)) there is no knowledge of the
- contents of the archives, so the ``creator'' cannot replay the
- archive, however ppppmmmmcccchhhhaaaarrrrtttt(1) is able to replay any archive, and so this
- tool is identified as the CCCCrrrreeeeaaaattttoooorrrr:::: for archive folios created by
- mmmmkkkkaaaaffff(1).
-
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- MMMMKKKKAAAAFFFF((((1111)))) MMMMKKKKAAAAFFFF((((1111))))
-
-
-
- 6. This is then followed by one or more lines beginning with the tag
- AAAArrrrcccchhhhiiiivvvveeee:::: followed by the hostname and base name of the archive.
-
- For example
- $ mkaf mydir/gonzo
- might produce the following folio control file.
-
- PCPFolio
- Version: 1
- # use pmafm(1) to process this PCP archive folio
- #
- Created: on gonzo at Tue Jul 2 03:35:54 EST 1996
- Creator: pmchart
- # Host Basename
- #
- Archive: gonzo mydir/gonzo/960627
- Archive: gonzo mydir/gonzo/960628
- Archive: gonzo mydir/gonzo/960629
- Archive: gonzo mydir/gonzo/960630
- Archive: gonzo mydir/gonzo/960701
- Archive: gonzo mydir/gonzo/960701.00.10
- Archive: gonzo mydir/gonzo/960701.05.25
- Archive: gonzo mydir/gonzo/960702.00.10
-
- PPPPCCCCPPPP EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT
- Environment variables with the prefix PPPPCCCCPPPP____ are used to parameterize the
- file and directory names used by PCP. On each installation, the file
- /_e_t_c/_p_c_p._c_o_n_f contains the local values for these variables. The
- $$$$PPPPCCCCPPPP____CCCCOOOONNNNFFFF variable may be used to specify an alternative configuration
- file, as described in ppppccccpppp....ccccoooonnnnffff(4).
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- ffffiiiinnnndddd(1), oooovvvviiiieeeewwww(1), PPPPCCCCPPPPIIIInnnnttttrrrroooo(1), ppppmmmmaaaaffffmmmm(1), ppppmmmmcccchhhhaaaarrrrtttt(1), ppppmmmmvvvviiiieeeewwww(1),
- ppppccccpppp....ccccoooonnnnffff(4) and ppppccccpppp....eeeennnnvvvv(4).
-
- DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
- Some informational messages, warnings and pathological conditions are
- reported on standard error.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-